Link policy routing based on link utilization

ABSTRACT

In one embodiment, a link utilization threshold is assigned to a first link. Link utilization of the first link and of one or more second links is monitored. The first link is considered to be out-of-policy (OOP) in the event that the link utilization of the first link surpasses the link utilization threshold. In response to the first link being considered OOP, action is taken. An excess utilization of the first link is determined. One or more prefixes currently routed over the first link whose collective per prefix utilization exceeds the excess utilization are determined. Provided that the collective per prefix utilization of the one or more prefixes currently routed over the first link, if added to the link utilization of the one or more second links, would not cause the one or more second links to be considered OOP, the one or more prefixes are redirected over them.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.11/337,217, entitled LINK POLICY ROUTING BASED ON LINK UTILIZATION,filed by Patel et al. on Jan. 20, 2006, the contents of which are herebyincorporated in its entirety. U.S. patent application Ser. No.11/337,217 claims the benefit of U.S. Provisional Application Ser. No.60/679,184, entitled SYSTEMS AND METHODS FOR USE WITH OPTIMIZED EDGEROUTING, filed by Blair et al. on May 9, 2005, the contents of which arealso hereby incorporated in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to computer networks and more particularlyto link policy routing based on link utilization in a computer network.

2. Background Information

A computer network is a geographically distributed collection of nodesinterconnected by communication links and segments for transporting databetween end nodes, such as personal computers and workstations(“hosts”). Many types of networks are available, with the types rangingfrom local area networks (LANs) to wide area networks (WANs). LANstypically connect the nodes over dedicated private communications linkslocated in the same general physical location, such as a building orcampus. WANs, on the other hand, typically connect geographicallydispersed nodes over long-distance communications links, such as commoncarrier telephone lines, optical lightpaths, synchronous opticalnetworks (SONET), or synchronous digital hierarchy (SDH) links. TheInternet is an example of a WAN that connects disparate networksthroughout the world, providing global communication between nodes onvarious networks. The nodes typically communicate over the network byexchanging discrete frames or packets of data according to predefinedprotocols, such as the Transmission Control Protocol/Internet Protocol(TCP/IP). In this context, a protocol consists of a set of rulesdefining how the nodes interact with each other. Computer networks maybe further interconnected by an intermediate network node, such as arouter, to extend the effective “size” of each network.

Since management of interconnected computer networks can proveburdensome, smaller groups of computer networks may be maintained asrouting domains or autonomous systems. The networks within an autonomoussystem (AS) are typically coupled together by conventional “intradomain”routers configured to execute intradomain routing protocols, and aregenerally subject to a common authority. To improve routing scalability,a service provider (e.g., an ISP) may divide an AS into multiple“areas.” It may be desirable, however, to increase the number of nodescapable of exchanging data; in this case, interdomain routers executinginterdomain routing protocols are used to inter-connect nodes of thevarious ASes. Moreover, it may be desirable to interconnect various ASesthat operate under different administrative domains. As used herein, anAS or an area is generally referred to as a “domain,” and a node thatinterconnects different domains together is generally referred to as a“border node” or “border router.” In general, the autonomous system maybe an enterprise network, a service provider or any other network orsubnetwork. Furthermore, the autonomous system may be multi-homed, i.e.,comprising a plurality of different peer (neighboring) connections toone or more other routing domains or autonomous systems.

The administrative entity of an AS typically configures network nodeswithin the AS to route packets using predetermined intradomain routingprotocols, or interior gateway protocols (IGPs), such as conventionallink-state protocols and distance-vector protocols. These IGPs definethe manner with which routing information and network-topologyinformation is exchanged and processed in the AS. Examples of link-stateand distance-vectors protocols known in the art are described inSections 12.1-12.3 of the reference book entitled Interconnections,Second Edition, by Radia Perlman, published January 2000, which ishereby incorporated by reference as though fully set forth herein.

Link-state protocols, such as the Open Shortest Path First (OSPF)protocol, use cost-based routing metrics to determine how data packetsare routed in an AS. As understood in the art, a relative cost value maybe associated with a network node to determine the relative ease/burdenof communicating with that node. For instance, the cost value may bemeasured in terms of the average time for a data packet to reach thenode, the amount of available bandwidth over a communication linkcoupled to the node, the monetary cost per amount of bandwidth, etc.Network nodes in the AS generate a set of cost values associated withtheir neighboring nodes. Each set of cost values is then “advertised”(flooded) to the other interconnected nodes. Using the advertised costvalues, each node can generate a consistent “view” of the networktopology, thereby enabling the nodes to determine lowest-cost routeswithin the AS.

Distance-vector protocols, such as the Interior Gateway Routing Protocol(IGRP) or Routing Information Protocol (RIP), use distance-based routingmetrics to determine how data packets are routed in an AS. A networknode may associate a distance metric with each of its interconnectednodes in the AS. For example, the distance metric may be based on, e.g.,a number of hops between a pair of nodes or an actual distanceseparating the nodes. Operationally, the network nodes determinedistances to reachable nodes in the AS and communicate these distancemetrics to their neighboring nodes. Each neighboring node augments thereceived set of distance metrics with its own distance measurements andforwards the augmented set of metrics to its neighbors. This process iscontinued until each node receives a consistent view of the networktopology.

An intermediate network node often stores its routing information in arouting table maintained and managed by a routing information base(RIB). The routing table is a searchable data structure in which networkaddresses are mapped to their associated routing information. However,those skilled in the art will understand that the routing table need notbe organized as a table, and alternatively may be another type ofsearchable data structure. Although the intermediate network node'srouting table may be configured with a predetermined set of routinginformation, the node also may dynamically acquire (“learn”) networkrouting information as it sends and receives data packets. When a packetis received at the intermediate network node, the packet's destinationaddress may be used to identify a routing table entry containing routinginformation associated with the received packet. Among other things, thepacket's routing information indicates the packet's next-hop address.

A plurality of interconnected ASes may be configured to exchange routingand reachability information among neighboring interdomain routers ofthe systems in accordance with a predetermined external gatewayprotocol, such as the Border Gateway Protocol (BGP). The BGP protocol iswell known and generally described in Request for Comments (RFC) 1771,entitled A Border Gateway Protocol 4 (BGP-4), published March 1995,which is hereby incorporated by reference in its entirety. An adjacencyis a relationship formed between selected neighboring (peer) routers forthe purpose of exchanging routing information messages and abstractingthe network topology. The routing information exchanged by BGP peerrouters typically includes destination address prefixes, i.e., theportions of destination addresses used by the routing protocol to renderrouting (“next hop”) decisions. Examples of such destination addressesinclude IP version 4 (IPv4) and version 6 (IPv6) addresses. BGPgenerally operates over a reliable transport protocol, such as TCP, toestablish a TCP connection/session. To implement the BGP protocol, eachAS includes at least one border node through which it communicates withother, interconnected ASes. Because data packets enter and exit the ASthrough the border node, the border node is said to be located at the“edge” of the AS.

The BGP protocol generally facilitates policy-based routing in which anadministrative entity places restrictions on inter-AS routingoperations. For example, the administrator of a company's AS may employa BGP routing policy where network traffic leaving the AS is notpermitted to enter a competitor's network, even if the competitorprovides an otherwise acceptable routing path. BGP policies typically donot depend on the cost-based or distance-based routing metrics used withinterior gateway protocols. Instead, the BGP policies rely on ASpath-vector information. More specifically, the BGP protocol enables aplurality of interconnected ASes to exchange network topologyinformation. Using this topology information, each AS can derive “paths”to the other reachable ASes, each path defining a logical sequence ofASes. For example, a path between an AS1 and an AS3 may be representedby the sequence {AS1, AS2, AS3} when only AS2 intervenes. Based on thecontent of these AS sequences, the BGP protocol may filter those pathsthat do not coincide with the administrator's policies. As such,inter-AS routing operations are performed using only the “best paths”that satisfy the BGP policies.

Because BGP policies are applied to sequences of ASes, the policies arenot able to optimize inter-AS routing in other respects, such asoptimizing bandwidth utilization or minimizing cost or distance metrics.Furthermore, interior gateway protocols cannot remedy these deficienciesin the BGP protocol because they do not scale well when applied to alarge number of network nodes spanning multiple ASes. For instance, theprocess of exchanging cost-based or distance-based routing metrics amonga large number of network nodes would not only consume an unreasonableamount of network bandwidth, but also would consume an unacceptableamount of processing resources for processing those metrics to generatea convergent view of the network topology.

To address the limitations of conventional routing protocols, networkadministrators sometimes implement additional optimizations to improvenetwork performance. For example, a load-balancing or cost-minimizingprocedure may be used in conjunction with traditional routing protocolsto redistribute data flows entering or exiting a multi-homed routingdomain or AS. In some networks, border nodes located at edges of ASes,e.g., between an enterprise network and one or more Internet ServiceProviders (ISPs), may be configured as Optimized Edge Routers (OERs).Here each OER may be configured to periodically select an Optimal ExitLink (OEL) to each ISP for a given destination prefix (a monitoredprefix) based on performance, load, cost, and service level agreements(SLAs) associated with connections to the ISP. Ultimately, the endresult for the enterprise network is improved Internet performance,better load distribution, and/or lower costs for Internet connections.These additional procedures may require the border nodes (OERs) tocollect various network statistics associated with the data flows. Anexemplary software application that may be used to collect the networkstatistics at the border nodes is NetFlow™ by Cisco Systems,Incorporated, which is described in more detail in the technical paperentitled Netflow Services Solutions Guide, published September 2002, andis hereby incorporated by reference as though fully set forth herein.

Techniques that may be used to select the OEL for the monitored prefixinclude passive monitoring and/or active probing. Passive monitoringrelies on gathering information from OERs learned from monitoringconventional user traffic, such as through-put, timing, latency, packetloss, reachability, etc. For example, selected interfaces at one or morenetwork nodes monitor incoming and outgoing data flows and collectvarious statistics for the monitored flows. Notably, interfaces mayinclude physical interfaces, such as a port on a network interface card,and/or logical interfaces, such as virtual private networks (VPN)implemented over multiple physical interfaces. Each node stores addressprefixes and statistics for the monitored data flows, which may beperiodically exported to a central management node (e.g., a “collector”or “Master”). The central management node is configured to receiveprefixes and statistics from a plurality of different network nodes. Arecord format that may be used to export the raw prefixes and statisticsis described in the technical paper entitled Netflow v9 Export Format,which is hereby incorporated by reference in its entirety. Further, amore sophisticated interaction (e.g., a filtered and/or pre-processedinformation exchange) between border nodes and a Master node isdescribed in commonly owned copending U.S. patent application Ser. No.10/980,550, entitled METHOD AND APPARATUS FOR AUTOMATICALLY OPTIMIZINGROUTING OPERATIONS AT THE EDGE OF A NETWORK, filed by Shah et al. onNov. 3, 2004, now issued as U.S. Pat. No. 8,073,968, the contents ofwhich are hereby incorporated in its entirety.

Active probing, on the other hand, relies on probe packets to measurevarious parameters associated with accessing the monitored prefix froman originating node (source). Here, the originating node may generatemultiple probe packets that are then forwarded via different exitinterfaces (e.g., data links) on different paths to target nodes(targets) in the monitored (destination) prefix. Upon receiving theprobe packets, the targets respond to the originating node, e.g., withreturn packets or other known probe responses. The originating node mayeventually acquire the responses and use them to measure variousparameters, such as delay, loss, jitter, and reachability, etc.,associated with accessing the destination prefix via the differentlinks.

Once the relevant statistics are obtained (e.g., at the centralmanagement node), the collected parametric (performance) information(i.e., learned from passive monitoring or active probing) is analyzed,such as either manually by a network administrator or dynamically by asoftware script. The analyzed information may then be used to select anOEL from among the different exits that may be used to reach thedestination prefix, and/or to determine whether the data flows may bemore optimally distributed. For instance, suppose an administratordesires to make more efficient use of available network bandwidth anddetermines that a first network interface is under-utilized and a secondinterface is oversubscribed. In this case, at least some data flows atthe second interface may be redirected to the first interface. Toeffectuate such a routing change, the administrator may, for example,make static changes to the routing tables at the first and secondinterfaces or may re-assign local-preference values (or other priorityvalues) associated with the data flows.

Currently, to determine whether certain links are under- orover-utilized, the administrator manually examines the data flows anddecides whether to redirect traffic. Conventional dynamic routingprotocols, including OER, may select the best link for one or moreprefixes in real time. Often, however, the best link (e.g., an OEL) fora particular prefix may also be the best link for many other prefixes,such as, e.g., where any of the cost, delay, jitter, etc. are morefavorable to that link than to other links. Because of this, the bestlink may quickly become congested and over-utilized withoutadministrator intervention. Once 100% utilization capacity is reached(e.g., 100 Kilobytes per second, KBps, of traffic over a 100 KBps link),packets within the data flow may be dropped, delayed, etc. Upon learningof the loss, delay, etc. of the selected best link, the routingprotocols may no longer select that link as the best, and may move thetraffic to other link with less loss, delay, etc. (e.g., as is the casewith OER). This process is sub-optimal, in that it allows packets to bedropped or delayed before any action is performed, if any action isperformed at all.

Further, while there are existing means for balancing traffic across aplurality of links, none of the current means are adaptive to the actual(and real time) traffic and/or utilization of the links. For instance,packet based or flow based load balancing generally requires that theplurality of links have equal costs. Although this may be useful forvarious network configurations (e.g., core networks), the scalability ofthese means is limited.

There remains a need, therefore, for a technique that prevents a linkfrom reaching its utilization capacity, thus reducing the number ofdropped packets and delay over the link. Also, there remains a need fora technique that proportionally load balances traffic across a pluralityof links in the case where links have unequal properties(costs/capacities, etc.), and that is adaptive to the flow of traffic.

SUMMARY OF THE INVENTION

The present invention is directed to a technique for dynamicallyapplying a link utilization based policy to traffic traversing links ina computer network. According to the novel technique, a link utilizationthreshold is assigned to one or more links. The link utilizationthreshold may be, for example, a maximum amount of traffic for anindividual link, or a maximum difference between links (e.g., for loadbalanced traffic). The link utilization of the one or more links may bemonitored, such as, e.g., by an optimized edge routing (OER) process. Inthe event that the link utilization surpasses the threshold, the link isconsidered to be out-of-policy (OOP), and traffic may be redirected toother available links accordingly in order to bring the link back inpolicy (“IN-POLICY”).

In accordance with one aspect of the present invention, a linkutilization threshold is assigned to each individual link that is, e.g.,a percentage of the total capacity of the link, an absolute bandwidthvalue, etc. The link utilization is monitored, and if the utilization isabove the threshold, the link is considered to be OOP. Excessutilization for an OOP link may be reduced by changing the routes of oneor more selected prefixes, i.e., to use other available links. Notably,care may be taken so as to avoid “blackholing” prefixes, as will beunderstood by those skilled in the art.

In accordance with another aspect of the present invention, a loadbalancing link utilization threshold (or range) is assigned to one ormore links that is, e.g., a percent difference between other selectedlinks (“load balanced links”) (e.g., a percentage of the total capacityof a link that is greater than that of another link by a configurableamount), an absolute bandwidth difference (e.g., a configurable amountof used bandwidth greater than that of another link), etc. The loadbalancing link utilization is monitored, and if the utilizationsurpasses the threshold for a link, that link is considered to be OOP,and prefix routes may be changed accordingly. Optionally, the routechanges may be configured to bring the link utilization of the selectedload balanced links as close to equal/proportional as desired (e.g.,percent usage or absolute bandwidth), or instead configured to simplyreduce the difference to below the configured threshold.

Advantageously, the novel technique dynamically applies a linkutilization based policy to traffic traversing links in a computernetwork. By defining link utilization thresholds, the novel techniquedynamically prevents a link from reaching its utilization capacity, thusreducing the number of dropped packets and delay over the links. Also,by defining load balancing thresholds, the novel technique mayproportionally load balance traffic based on link capacity, especiallyin the case where links have unequal capacities, where other currentmethods fail. Further, the novel technique is adaptive to the flow oftraffic and does not depend upon traditional (and often cumbersome)routing techniques to load balance traffic among a plurality of unequallinks (e.g., in capacity and/or cost).

BRIEF DESCRIPTION OF THE DRAWINGS

The above and further advantages of the invention may be betterunderstood by referring to the following description in conjunction withthe accompanying drawings in which like reference numerals indicateidentically or functionally similar elements, of which:

FIG. 1 is a schematic block diagram of an exemplary computer networkthat may be advantageously used with the present invention;

FIG. 2 is a schematic block diagram of an exemplary node that may beadvantageously used with the present invention;

FIG. 3 is an exemplary link policy table that may be used in accordancewith the present invention;

FIGS. 4A-4B are graphical representations of link utilization and linkpolicy for individual links in accordance with the present invention;

FIGS. 5A-5C are graphical representations of link utilization and linkpolicy for load balanced links in accordance with the present invention;and

FIG. 6 is a flowchart illustrating a procedure for dynamically applyinga link utilization based policy to traffic traversing links inaccordance with the present invention.

DETAILED DESCRIPTION OF AN ILLUSTRATIVE EMBODIMENT

FIG. 1 is a schematic block diagram of an exemplary computer network 100comprising an autonomous system (AS) AS 1 (e.g., an enterprise orcontent provider network) interconnected to one or more destinationprefixes (e.g., within one or more content consumer networks). AlthoughAS1 is illustratively an autonomous system, those skilled in the artwill appreciate that AS1 may be configured as one or more routingdomains or other networks or subnetworks. AS1 comprises one or morenetwork nodes, including a set of communicating border nodes(illustratively, edge or border routers, BRs) BR1 and BR2, through whichclient communications, such as data packet traffic, can pass into andout of the AS. For example, BR1-BR2 permit communication from AS1to/from destination prefixes (e.g., via a wide area network, or WAN),such as through illustrative exits (“links”) 1 and 2 on BR1, and links 3and 4 on BR2. Routing operations at the border nodes BR1-BR2 may bemanaged by an optimized edge routing (OER) “Master” node, which may beconnected to the border nodes by, e.g., point-to-point links or a localarea network. Also, BR1-BR2 may be in communication with each other,such as through illustrative links as shown. These examples are merelyrepresentative. Those skilled in the art will understand that any numberof routers, nodes, links, and exits may be used in the computer networkand connected in a variety of ways, and that the view shown herein isfor simplicity.

Data packets may be communicated by the AS and destination prefixesusing pre-defined network communication protocols such as theTransmission Control Protocol/Internet Protocol (TCP/IP), User DatagramProtocol (UDP), Asynchronous Transfer Mode (ATM) protocol, Frame Relayprotocol, Internet Packet Exchange (IPX) protocol, etc. Routingdecisions within an AS may rely on predetermined “interior” gatewayprotocols (IGPs), such as conventional link-state or distance-vectorprotocols. In addition, data packets containing network topologyinformation may be exchanged among ASes using “external” gatewayprotocols, such as the Border Gateway Protocol (BGP).

FIG. 2 is a schematic block diagram of an exemplary node 200 that may beadvantageously used with the present invention, such as, e.g., a bordernode (e.g., an edge router) or a master node. The node comprises aplurality of network interfaces 210 a-n (e.g., line cards), a processor220, and a memory 240 interconnected by a system bus 250. The networkinterfaces 210 contain the mechanical, electrical and signalingcircuitry for communicating data over physical links coupled to thenetwork 100, and also may be adapted to process the incoming andoutgoing data. The network interfaces may be further configured totransmit and/or receive data using a variety of different communicationprotocols, including, inter alia, TCP/IP, UDP, ATM, synchronous opticalnetworks (SONET), wireless protocols, Frame Relay, Ethernet, FiberDistributed Data Interface (FDDI), etc. Notably, a physical networkinterface 210 may also be used to implement one or more virtual networkinterfaces, such as for virtual private network (VPN) access, known tothose skilled in the art. Both physical network interfaces and virtualnetwork interfaces (e.g., routes out of an edge router) are referred togenerally herein as “exits” or “links.”

The memory 240 comprises a plurality of storage locations that areaddressable by the processor 220 and the network interfaces 210 forstoring software programs and data structures associated with thepresent invention. The processor 220 may comprise necessary elements orlogic adapted to execute the software programs and manipulate the datastructures, such as link policy table 300. An operating system 242(e.g., the Internet-working Operating System, or IOS™, of Cisco Systems,Inc.), portions of which are typically resident in memory 240 andexecuted by the processor, functionally organizes the router by, interalia, invoking network operations in support of software processesand/or services executing on the router. These software processes and/orservices may include Routing Information Base (RIB) 245, OER/Master OERProcess 246, and routing services 247. It will be apparent to thoseskilled in the art that other processor and memory means, includingvarious computer-readable media, may be used to store and executeprogram instructions pertaining to the inventive technique describedherein.

Routing services 247 contain computer executable instructions executedby processor 220 to perform functions provided by one or more routingprotocols, such as OSPF, IS-IS, IP, BGP, etc. These functions may beconfigured to manage a forwarding information database (not shown)containing, e.g., data used to make forwarding decisions. The RIB 245maintains copies of routes (paths) provided by the routing protocols,such as IGP or BGP, in order to compute best paths/routes forinstallation into the routing table (not shown).

According to the illustrative embodiment of the present invention, theOER/Master OER Process 246 is employed by an OER node (e.g., borderrouters BR1-BR2) and an OER Master node (e.g., an OER Master router orMaster Controller), respectively. The Master OER process 246 executingon the OER Master node communicates with border routers BR1-BR2 torequest, among other things, the monitoring of a set of addressprefixes. The OER processes 246 executing on the border routers monitortraffic at the edge of the AS1 and respond with, inter alia, networkstatistics corresponding to the monitored prefixes. Illustratively,instances of the OER process 246 execute on the network interfaces 210as OER processes 211 a-n configured to measure various types of networkstatistics acquired from monitored traffic. These statistics are thenforwarded from the OER processes 211 a-n to the OER process 246. Thestatistics may correspond to various traffic measurements, such asround-trip delay times, data throughput (i.e., the amount of datatransferred or received), packet loss, reachability, etc. In general,the OER processes (notably, 246 and/or 211 a-n) may measure anyarbitrary traffic metric, including conventional cost-based anddistance-based metrics. Further, the OER Process 246 and/or 211 a-n maycalculate statistical averages, variances, medians, etc. of a collectionof traffic measurements.

Techniques for learning address prefixes and collecting trafficstatistics (passively monitoring) are described in commonly-ownedcopending U.S. patent application Ser. No. 10/980,550, entitled METHODAND APPARATUS FOR AUTOMATICALLY OPTIMIZING ROUTING OPERATIONS AT THEEDGE OF A NETWORK, filed by Shah et al. on Nov. 3, 2004, now issued asU.S. Pat. No. 8,073,968, the contents of which are hereby incorporatedin its entirety. Also, techniques for actively probing (managing pathsand targets of active probe packets) are described in commonly-ownedcopending U.S. patent application Ser. No. 11/113,629, entitled ACTIVEPROBE PATH MANAGEMENT, filed by Blair et al. on April 25, 2005, nowissued as U.S. Pat. No. 7,619,982, and commonly owned copending U.S.patent application Ser. No. 11/113,582, entitled ACTIVE PROBE TARGETMANAGEMENT, filed by Metzger et al. on Apr. 25, 2005, now issued as U.S.Pat. No. 7,675,861, the contents of both of which are herebyincorporated in their entirety.

The statistics from the OER Process 246 and/or 211 a-n are thenprocessed at the Master node in accordance with the Master OER process246. More specifically, the Master OER process 246 analyzes thestatistics and determines whether the distribution of traffic enteringand/or leaving the AS1 can be optimized, e.g., according to one or morepolicies. If so, the Master OER process may redistribute traffic routedthrough the border nodes by, e.g., associating new BGP local-preferencevalues with selected traffic or statically changing the routing tablecontents of the border nodes, as described in detail below. In thatsense, the Master OER process selects optimal exit links (OELs) (“bestexits”) to various destination prefixes. Notably, the Master OER process246 may be distributed among a plurality of nodes, and thus need notreside in a single OER Master node. Also, it is not necessary for asingle OER Master node to contain routing processes or routing tables,other than what is necessary for communication with the border nodes.Those skilled in the art will understand that while the OER Master nodeand OER node (e.g., a border router) are shown as separate nodes (e.g.,in FIG. 1), the Master and OER node may be configured within the samenode. For example, a single border router (e.g., a home office router)having multiple exits/paths may both monitor the quality of its exitsand select the OEL itself.

The present invention is directed to a technique for dynamicallyapplying a link utilization based policy to traffic traversing links ina computer network. According to the novel technique, a link utilizationthreshold is assigned to one or more links. The link utilizationthreshold may be, for example, a maximum amount of traffic for anindividual link, or a maximum difference between links (e.g., for loadbalanced traffic). The link utilization of the one or more links may bemonitored, such as, e.g., by an optimized edge routing (OER) process. Inthe event that the link utilization surpasses the threshold, the link isconsidered to be out-of-policy (OOP), and traffic may be redirected toother available links accordingly in order to bring the link back inpolicy (“IN-POLICY”).

In accordance with one aspect of the present invention, a linkutilization threshold is assigned to each individual link that is, e.g.,a percentage of the total capacity of the link, an absolute bandwidthvalue, etc. For example, a 100 Kilobytes per second (KBps) link (e.g.,Link 1) may have a link policy assigned as a 75% link utilizationthreshold, a 75 KBps link utilization threshold, etc. Also, whenpolicies are applied to more than one link, different thresholds may beassigned to each of the links accordingly. For instance, a second link(e.g., an 80 KBps link, Link 2) may have an 80% link utilizationthreshold. Those skilled in the art will appreciate a common percentagemay be assigned to multiple links of varying bandwidth capacities, suchas, e.g., assigning a 75% link utilization threshold to both the 100KBps link and 80 KBps link.

FIG. 3 is an exemplary link policy table 300 that may be used inaccordance with the present invention. Table 300 is illustrativelystored in memory 240 and includes one or more entries 320, eachcomprising a plurality of fields for storing a link identification (ID)305, a link utilization threshold 310, and load balanced links 315 thatindicates with which other links the link ID 305 may be associated(described below). The table 300 is illustratively maintained andmanaged by OER/Master OER process 246. Those skilled in the art willunderstand that while a table is shown and described herein, other knowndata structures may be used in accordance with the present invention.Also, other link policy configurations, fields, link relations (e.g.,load balanced links), and values may be defined, as will be understoodby those skilled in the art, and the table 300 as shown is merelyrepresentative.

Link utilization may be monitored by various means, for example, byOER/Master OER process 246 described above. Alternatively, each node ofa network configured for link policy-based routing may also monitor linkutilization for its links by available monitoring processes, such as,e.g., NetFlow™ by Cisco Systems, Inc. Notably, the process of monitoringmay be configured (e.g., by a system administrator) to be periodic asneeded, such as, e.g., every 30 seconds, or continuous for fasterresponse time. By comparing the monitored link utilization to theassigned thresholds (e.g., by OER process 246), it can be determinedthat the link is OOP in the event the link utilization surpasses thethreshold.

Once a link is OOP, excess utilization for the OOP link may be reducedby changing the routes of one or more selected prefixes, i.e., to useother available links. Illustratively, e.g., by using OER process 246, abandwidth utilization per prefix may be obtained by specificallymonitoring traffic flow to/from each of the prefixes (e.g., usingNetFlow™). With knowledge of per prefix bandwidth utilization, it ispossible to determine which prefix(es) to optimally redirect based onthe utilization of the prefix and the excess link utilization as awhole. For example, if the excess utilization of an OOP link is 10 KBps,and a particular prefix is utilizing 10 KBps of bandwidth of that link,it may be beneficial to move that one particular prefix to anotheravailable link. Similarly, two prefixes with a bandwidth utilization sumof 10 KBps (or greater) may be used, or three prefixes totaling 10 KBps,etc. While it feasible to move portions of a prefix or randomly selectedtraffic to another available link, a benefit of redirecting an entireprefix is that all traffic flowing to the particular prefix(es) will beredirected over the same link. As will be understood by those skilled inthe art, this provides various advantages, such as, e.g., reducedrouting complexity.

The prefix routes may be redirected until the OOP link is returned to anIN-POLICY state, e.g., at or below the link utilization threshold. Aconfigurable amount below the threshold may be put into effect by asystem administrator such that once the link is considered to be OOP,the traffic is redirected until the link utilization of the OOP link isat least the configurable amount below the threshold. In this manner,the previously OOP link is less likely to quickly surpass the linkutilization threshold and become OOP again due to increased traffic flowover a short time.

As will be understood by those skilled in the art, it is important toensure that by redirecting traffic to other links, those other links donot become OOP as well. If those links were to become OOP, undesirablenetwork oscillations and/or churn may result as the traffic isredirected from one OOP link to another OOP link. By first confirmingthat the newly redirected traffic does not force another available linkto become OOP, such undesirable outcomes may be obviated. Notably, inthe event that there are no available links that would not become OOP(i.e., all available links are already OOP), traffic may not beredirected anywhere, and an error may be returned to the system, suchthat a system administrator may take corrective action (e.g., raisethresholds or add bandwidth). Also, care may be taken so as to avoid“blackholing” prefixes, as will be understood by those skilled in theart. Blackholing, generally, is a term of art that denotes traffic thatis lost en route to a destination, such as, e.g., when the destinationprefix is not reachable over the path selected. Therefore, by firstensuring that the destination is reachable by the other available linksprior to transferring traffic to reduce the OOP link utilization,blackholing of the traffic may be avoided.

As an example, FIGS. 4A-4B are graphical representations of linkutilization and link policy for individual links in accordance with thepresent invention. Referring again to FIG. 3, Link 1 (e.g., 100 KBps)and Link 2 (e.g., 80 KBps) have link utilization thresholds of 75% and80%, respectively. Assume, as in FIG. 4A, that Link 1 has a utilizationof 80% (80 KBps), and Link 2 has a utilization of 40% (32 KBps). Here,Link 1 is OOP with 5% (5 KBps) excess traffic above the utilizationthreshold. According to the present invention, one or more prefixes witha total bandwidth utilization of 5 KBps (or more) are selected to beredirected over one or more other available links, e.g., Link 2.Illustratively, as shown in FIG. 4B, one or more prefixes totaling 12KBps of utilization are redirected from OOP Link 1 to available Link 2.The 12 KBps may be selected because of a configurable amount below thethreshold that is needed to bring the OOP link IN-POLICY, or because thesmallest prefix to be redirected had a bandwidth utilization of 12 KBps,etc. Upon redirecting the traffic, the link utilizations for Link 1 andLink 2 are now 68% (68 KBps) and 55% (44 KBps), respectively, both undertheir assigned link utilization thresholds. Those skilled in the artwill understand that FIGS. 4A and 4B are merely representative example,and that other values and configurations may be used in accordance withthe present invention.

In accordance with another aspect of the present invention, a loadbalancing link utilization threshold (or range) is assigned to one ormore links, wherein the threshold is with regards to the linkutilization of one or more other selected links (“load balanced links”).The load balancing link utilization threshold may be configured as,e.g., a percent difference between load balanced links or an absolutebandwidth difference. For example, these differences may be embodied asa percentage of link capacity greater than the percentage of anotherload balanced link by a configurable percentage, an absolute amount ofbandwidth that is greater than the absolute amount of bandwidth ofanother load balanced link by a configurable percentage (or absoluteamount), etc. The load balancing link utilization is monitored asdescribed above, and again, if the utilization surpasses the thresholdfor a link, that link is considered to be OOP, and prefix routes may bechanged accordingly.

Optionally, the route changes may be configured to bring the linkutilization of the selected load balanced links as close toequal/proportional as desired (e.g., percent usage or absolutebandwidth), or instead configured to simply reduce the difference tobelow the configured threshold. For instance, once the link isconsidered OOP, traffic on the one or more selected load balanced links,including the OOP link, may be readjusted to equalize the loaddistribution (e.g., either in absolute bandwidth or proportionalpercentages), i.e., to the same percentage or bandwidth. Those skilledin the art will understand that other readjusting means are possible,such as lowering the difference between link utilization to aconfigurable amount below the load balancing link utilization threshold,as mentioned above. Also, as mentioned above, it is important to ensurethat by redirecting traffic to other load balanced links, that thoseother links do not become OOP as well.

As an example, FIGS. 5A-5C are graphical representations of linkutilization and link policy for load balanced links in accordance withthe present invention. Referring again to FIG. 3, Link 3 (e.g., 100KBps) and Link 4 (e.g., 100 KBps) both have load balancing linkutilization thresholds of no more than 20% greater than the other loadbalanced link. Assume, as in FIG. 5A, that Link 3 has a utilization of84% (84 KBps), and Link 4 has a utilization of 60% (60 KBps). Here, Link3 has a link utilization that is greater than Link 4 by 24%. In otherwords, Link 3 is OOP by 4% (4 KBps) excess traffic above the loadbalancing link utilization threshold. According to the presentinvention, one or more prefixes with a total bandwidth utilization of 2KBps (or more) are selected to be redirected over one or more otheravailable load balanced links, e.g., Link 4. Those skilled in the artwill appreciate that 4 KBps of excess utilization requires that half ofthe excess traffic (in the case of two load balanced links) beredirected, i.e., 2 KBps. Illustratively, as shown in FIG. 5B, one ormore prefixes totaling 2 KBps of utilization are redirected from OOPLink 3 to load balanced Link 4, thus reducing the difference to withinthe threshold, 20%. Upon redirecting the traffic, the link utilizationfor Link 3 and Link 4 are now 82% (82 KBps) and 62% (62 KBps),respectively, which is within the load balancing link utilizationthreshold. Briefly, FIG. 5C shows a configuration where the OOP Link 3triggers the redirection of traffic that brings the load balanced linksto an equal/proportional value (i.e., a difference of 0%), as mentionedabove. Here, 12 KBps of traffic is redirected from Link 3 to Link 4,such that both load balanced links have equal link utilization of 72%(72 KBps). Those skilled in the art will understand that FIGS. 5A, 5B,and 5C are merely representative example, and that other values andconfigurations may be used in accordance with the present invention.

With further reference again to FIG. 3, entries 320 for Link N and LinkX (not shown in FIG. 1) represent one or more possible link policyconfigurations not discussed in detail above. Those skilled in the artwill understand that still other configurations and values may be usedin accordance with the present invention, and that any configurationsand values described herein are merely representative. For example,entries for Link N demonstrate that more than one entry for each Link ID305 may be within the table 300. For instance, an individual linkutilization threshold of 85 KBps may be assigned to Link N, as well as aload balancing link utilization threshold of no more than 20% greaterthan either load balanced Link Y or Z (also not shown). Still, Link Nmay also be separately load balanced with a Link X (not shown), e.g., bynot more than 15 KBps greater than Link X, while Link X may be assigneda different load balancing link utilization threshold with regard toLink N, e.g., by not more than 25% greater than Link N. Again, thesereferences are meant to be further examples of possible link policyconfigurations, and are not meant to be limiting on the scope of thepresent invention.

Notably, in addition to percentages, differences, and absolute values asdescribed above, the link utilization threshold of the present inventionmay also be set as a relative link utilization policy, where aconfigurable increase (e.g., a spike or slow increase) in linkutilization or in the difference of link utilizations between two loadbalanced links triggers an OOP event. Relative policies are described indetail in commonly-owned copending U.S. patent application Ser. No.11/239,613, entitled TECHNIQUE FOR MAINTAINING AND ENFORCING RELATIVEPOLICIES WITH THRESHOLDS, filed by Xia et al. on Sep. 29, 2005, thecontents of which are hereby incorporated in its entirety.

Also, a minimum threshold may be assigned to a link in order to preventunder-utilization of the link, which may be beneficial under certaincircumstances that will be understood by those skilled in the art. Forexample, a system administrator may wish to more evenly distribute linkutilization among a plurality of links, e.g., such as during loadbalancing traffic. By placing a minimum threshold on the links (e.g.,20%), a link would be considered OOP if not enough traffic wereutilizing that link. Thus, to bring the link back IN-POLICY, trafficwould be redirected onto the link from other links.

FIG. 6 is a flowchart illustrating a procedure for dynamically applyinga link utilization based policy to traffic traversing links inaccordance with the present invention. The procedure 600 starts at step605, and continues to step 610, where link utilization thresholds areassigned to one or more links (e.g., a percentage, absolute value, ordifference, as described above). Once the thresholds are established,the link utilization of the one or more links is monitored at step 615,such as, e.g., by OER process 246. As mentioned above, the monitoringmay be continuous or periodic, depending upon configuration. If theutilization does not surpass the assigned threshold for a particularlink at step 620, the link utilization continues to be monitored at step615. If, on the other hand, the link utilization does surpass theassigned threshold at step 620, the link is considered to be OOP in step625. Upon considering the link OOP, traffic may then be redirected toother available links accordingly to bring the OOP link back IN-POLICY.Notably, for load-balanced traffic, IN-POLICY may require a differenceless than a configurable amount, or simply a difference below thethreshold, as described above. Further, as mentioned above, measures maybe taken to ensure that other links do not surpass their utilizationthresholds during the redirection, and to ensure that no prefixes are“blackholed.” The procedure may then return to step 615 to continuemonitoring the link utilization of the one or more links.

Advantageously, the novel technique dynamically applies a linkutilization based policy to traffic traversing links in a computernetwork. By defining link utilization thresholds, the novel techniquedynamically prevents a link from reaching its utilization capacity, thusreducing the number of dropped packets and delay over the links. Also,by defining load balancing thresholds, the novel technique mayproportionally load balance traffic based on link capacity, especiallyin the case where links have unequal capacities, where other currentmethods fail. Further, the novel technique is adaptive to the flow oftraffic and does not depend upon traditional (and often cumbersome)routing techniques to load balance traffic among a plurality of unequallinks (e.g., in capacity and/or cost).

While there has been shown and described an illustrative embodiment thatdynamically applies a link utilization based policy to traffictraversing links in a computer network, it is to be understood thatvarious other adaptations and modifications may be made within thespirit and scope of the present invention. For example, the inventionhas been shown and described herein illustratively using OER techniquesto monitor the utilization and to redirect traffic accordingly. However,the invention in its broader sense is not so limited, and may, in fact,be used with any monitoring processes and/or route optimizationtechniques, as will be understood by those skilled in the art. Also,while the invention has been shown and described for applying linkpolicies to individual links, the invention may, in fact, be used withgroups of links, as described in commonly-owned copending U.S. patentapplication Ser. No. 11/336,734, entitled LINK GROUPING FOR ROUTEOPTIMIZATION, filed by Shah on Jan. 20, 2006, the contents of which arehereby incorporated in its entirety. Further, those skilled in the artwill understand that the term “link” as used herein may indicate eithera physical link or virtual link.

The foregoing description has been directed to specific embodiments ofthis invention. It will be apparent, however, that other variations andmodifications may be made to the described embodiments, with theattainment of some or all of their advantages. For instance, it isexpressly contemplated that the teachings of this invention can beimplemented as software, including a computer-readable medium havingprogram instructions executing on a computer, hardware, firmware, or acombination thereof. Also, electromagnetic signals may be generated tocarry computer executable instructions that implement aspects of thepresent invention over, e.g., a wireless data link or a data network,such as the Internet. Accordingly this description is to be taken onlyby way of example and not to otherwise limit the scope of the invention.Therefore, it is the object of the appended claims to cover all suchvariations and modifications as come within the true spirit and scope ofthe invention.

1. A method comprising: assigning a link utilization threshold to afirst link; monitoring, by a processor, link utilization of the firstlink and of one or more second links; considering the first link to beout-of-policy (OOP) in the event that the link utilization of the firstlink surpasses the link utilization threshold of the first link; and inresponse to the first link being considered OOP, determining an excessutilization of the first link, determining one or more prefixescurrently routed over the first link whose collective per prefixutilization exceeds the excess utilization, determining that thecollective per prefix utilization of the one or more prefixes currentlyrouted over the first link, if added to the link utilization of the oneor more second links, would not cause the one or more second links to beconsidered OOP, and redirecting the one or more prefixes currentlyrouted over the first link to thereafter be routed over the one or moresecond links.
 2. The method of claim 1, further comprising: determiningthat the one or more prefixes currently routed over the first link arereachable by the one or more second links prior to the redirecting. 3.The method of claim 1, wherein the redirecting routes each of the one ormore prefixes over a particular one of the one or more links, whereineach of the one or more prefixes is redirected over only one link. 4.The method of claim 1, wherein the link utilization threshold is apercentage of total capacity.
 5. The method of claim 1, wherein the linkutilization threshold of the first link differs from a link utilizationthreshold of the one or more second links.
 6. The method of claim 1,wherein the link utilization threshold is a relative threshold withrespect to one or more other links.
 7. The method of claim 1, whereinthe first link and the one or more second links are load balanced links,and the redirecting routes the one or more prefixes over the one or moresecond links to load balance traffic between the first link and the oneor more second links.
 8. The method of claim 1, wherein the determiningone or more prefixes further comprises: determining one or more prefixescurrently routed over the first link whose collective per prefixutilization exceeds the excess utilization by an amount sufficient tobring the link utilization of the first link below the link utilizationthreshold by at least a configurable amount.
 9. The method of claim 1,wherein the first link is a virtual link.
 10. The method of claim 1,further comprising: also considering the first link to be OOP in theevent that the link utilization of the first link falls below a minimumthreshold of the first link.
 11. An apparatus comprising: one or morenetwork interfaces; a processor coupled to the one or more networkinterfaces and configured to execute software processes; and a memoryconfigured to store an optimized edge routing (OER) process executableby the processor, the OER process operable to: monitor link utilizationof a first link coupled to one of the network interfaces, consider thefirst link to be out-of-policy (OOP) in the event that link utilizationof the first link surpasses a link utilization threshold of the firstlink; in response to the first link being considered OOP, determine anexcess utilization of the first link, determine particular trafficcurrently routed over the first link whose collective utilizationexceeds the excess utilization, determine that the collectiveutilization of the particular traffic currently routed over the firstlink, if added to the link utilization of the one or more second links,would not cause the one or more second links to be considered OOP, andredirect the particular traffic currently routed over the first link tothereafter be routed over the one or more second links.
 12. Theapparatus of claim 11, wherein the traffic currently routed over thefirst link is one or more prefixes currently routed over the first link.13. The apparatus of claim 12, wherein the OER process is furtheroperable to: determine that the one or more prefixes currently routedover the first link are reachable by the one or more second links. 14.The apparatus of claim 12, wherein each of the one or more prefixes isrouted over only one link of the one or more second links.
 15. Theapparatus of claim 11, wherein the link utilization threshold is apercentage of total capacity.
 16. The apparatus of claim 11, wherein thelink utilization threshold of the first link differs from a linkutilization threshold of the one or more second links.
 17. The apparatusof claim 11, wherein the link utilization threshold is a relativethreshold with respect to one or more other links.
 18. The apparatus ofclaim 11, wherein the first link and the one or more second links areload balanced links, and the OER process is further operable to redirectthe particular traffic to load balance traffic between the first linkand the one or more second links.
 19. The apparatus of claim 11, whereinthe first link is a virtual link.
 20. Software encoded on one or morenon-transitory computer readable media and when executed operable to:assign a link utilization threshold to a first link; monitor linkutilization of the first link and of one or more second links; considerthe first link to be out-of-policy (OOP) in the event that the linkutilization of the first link surpasses the link utilization thresholdof the first link; and in response to the first link being consideredOOP, determine an excess utilization of the first link, determine one ormore prefixes currently routed over the first link whose collective perprefix utilization exceeds the excess utilization, determine that thecollective per prefix utilization of the one or more prefixes currentlyrouted over the first link, if added to the link utilization of the oneor more second links, would not cause the one or more second links to beconsidered OOP, and redirect the one or more prefixes currently routedover the first link to thereafter be routed over the one or more secondlinks.